Description

We should be passing in a boolean value into the initial property for Confirm(): https://github.com/enquirer/enquirer/blob/70bdb0fedc3ed355d9d8fe4f00ac9b3874f94f61/lib/prompts/confirm.js#L8
However, since we convert it to a string, it will always evaluate to true and display Y/n for everything:

This is because ConfirmQuestionOptions expects a string for initial (it inherits from

). Looks like we are using an experimental version of the types definitions @ enquirer/enquirer#307. Kind of hacky, but I think it's ok for now if we want to keep things in sync with the PR?

If we want to fix it in the Types definition, I think we need to change initial?: T | ( () => Promise< T > | T ); to initial?: T | ( () => Promise< T > | T ) | boolean | ( () => Promise< boolean > | boolean ); under export type Question< T extends types.Answer = string, P extends Prompt< T > = Prompt< T > > = {
^ Happy to go about this way too and leave a comment in the PR

Pull request checklist

• Update SETUP.md with any new environmental variables.
• Update the documentation.
• Manually test the relevant changes.
• Follow the pull request checklist
• Add/update automated tests as needed.

New release checklist

• Automated tests pass.
• The Preparing for release checklist is completed.

Steps to Test

Outline the steps to test and verify the PR here.

Example:

1. Check out PR.
2. Run npm run build
3. Do vip dev-env create and expect to display as Enable Elasticsearch (needed by Enterprise Search)? (y/N)